This chapter describes the CONFIG process configuration and operational commands. It includes the following sections:
The Configuration process (CONFIG) is a second-level process of the device user interface. Using CONFIG commands, you can:
| Note: | Refer to the chapter "Migrating to a New Code Level" in 8371 Networking Multilayer Ethernet Switch Installation and Planning Guide for information about migrating to a new code level. |
CONFIG lets you display or change the configuration information stored in the device's nonvolatile configuration memory. Changes to system and protocol parameters do not take effect until you reload the device software. (For more information, refer to the OPCON reload command in "What is the OPCON Process?").
| Note: | You must enter the write command to save the changes in the device's flash memory. |
The CONFIG command interface is made up of levels that are called modes. Each mode has its own prompt. For example, the prompt for the SNMP protocol is SNMP config>.
If you want to know the process and mode you are communicating with, press Enter to display the prompt. Some commands in this chapter, such as the network and protocol commands, allow you to access and exit the various levels in CONFIG. See Table 13 for a list of the commands you can issue from the CONFIG process.
When the switch is booted, the following
interfaces are allocated:
Table 12. Interfaces Added at Boot Time
| Slot | Port | Device Type | Interface Number |
|---|---|---|---|
| 0 | 1-16 | 10/100MB Ethernet | 0-15 |
| 1 | 1-8 | 10/100MB Ethernet | 16-23 |
| 2 | 1-8 | 10/100MB Ethernet | 24-31 |
| 3 | 1-4 | LAG | 32-35 |
| 1 | 1-2 | ATM* | 36-37 |
| 2 | 1-2 | ATM* | 38-39 |
| 3 | 5-29 | LEC | 40-63 |
| Note: | * Only 2 ATM ports are supported at one time. You can have 4 independent configurations of ATM ports, but only 2 are active at any one time. |
When a feature card is hot-swapped into the switch, interface numbers are assigned from the above table. Feature cards can be added and removed to and from the feature card slots. However, the card being swapped must have been present at boot time, and only the same type of card may be swapped with the one being removed.
When a LEC is activated, the LEC must be associated with an ATM interface. The following default configuration values are associated with the LEC**:
| Note: | **These values guarantee that the box comes up with a known configuration. However, attempting to configure a LEC using all default values will probably fail. You need to provide network-specific information when configuring the LEC. See "Configuring and Monitoring LAN Emulation Clients" for LEC configuration detail. |
Quick Configuration (Quick Config) provides a minimal set of commands that allow you to configure bridging protocols and routing protocols present in the device load. You can also configure an SNMP community with WRITE_READ_TRAP access. This is useful during initial setup because the configuration program uses SNMP SET commands to transfer the configuration.
Quick Config complements the existing configuration process by offering a shortcut. This shortcut allows you to configure the minimum number of parameters for these bridging protocols and routing protocols without having to exit and enter the different configuration processes. The other parameters are set to selected defaults.
Quick Config operates as follows:
Quick Config sets a number of default parameters based upon how you answer the configuration questions. What cannot be configured with Quick Config can be configured using Config after exiting Quick Config.
You cannot delete Quick Config information from within Quick Config. However, you can correct information either by exiting and returning to Quick Config, or by entering the reload command as a response to some Quick Config questions.
You might want to run Quick Config manually to demonstrate the device's capabilities or to reconfigure dynamically to perform benchmark tests without having to learn the device's operating system commands.
To enter Quick Config, type qconfig at the Config> prompt.
To exit Quick Config, restart by entering r from any prompt. Follow the queries until you enter no and then enter q to quit. The router returns to either the Config (only)> or the Config> prompt.
The device configuration process allows for a maximum of 50 user names, passwords, and levels of permission. Each user needs to be assigned a password and level of permission. There are three levels of permission: Administration, Operation, and Monitoring.
If you are the system administrator, when you add a new user for the first time, you are asked if you want to add Technical Support access. If you answer yes, Technical Support is granted the same access privileges that you have as system administrator.
The password for this account is automatically selected by the software and is known by your service representative. This password can be changed using the change user command; however, if you do change the password, customer service cannot provide remote support. For additional information on the use of the change user command, see "Change".
Occasionally, you might need to change the configuration of a network interface along with its bridging and routing protocols without restarting the device. The reset command allows you to disable a network interface and then enable it using new interface, bridging and routing configuration parameters.
The interface, protocols and features configuration parameters are changed using the CONFIG process (talk 6) commands. The talk 6 commands affect the contents of the configuration memory. The configuration changes are activated by issuing the GWCON process (talk 5) reset command.
To reset an interface:
Example:
* configuration
Config> net 0
ATM User Configuration
ATM Config> le-client
ATM LAN Emulation Clients Configuration
LE Client config> config 6
. . . change ATM LAN Emulation Client parameters . . .
Ethernet Forum Compliant LEC Config> exit
LE Client config> exit
ATM Config> exit
| Note: | When using the configuration program, do the following to make configuration
changes to existing interfaces:
|
To enter the CONFIG process from OPCON and obtain the CONFIG prompt, enter the configuration command. Alternatively, you can enter the OPCON talk command and the PID for CONFIG. The PID for CONFIG is 6.
* configuration
or
* talk 6
The console displays the CONFIG prompt (Config>). If the prompt does not appear, press the Enter key again.
To exit CONFIG and return to the OPCON prompt (*), enter the intercept character. (The default is Ctrl-P .)
This section describes each of the CONFIG commands. Each command includes a description, syntax requirements, and an example. The CONFIG commands are summarized in Table 13.
After accessing the CONFIG environment, enter the configuration commands at
the Config> prompt.
Table 13. CONFIG Command Summary
| Command | Function |
|---|---|
| ? (Help) | Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help". |
| Add | Adds a user to the device. |
| Boot | Enters Boot CONFIG command mode. |
| Change | Changes a user's password or a user's parameter values associated with this interface. Also changes a slot/port of an interface. |
| Clear | Clears configuration information. Forces a re-boot for re-autoconfig. See Table 7. |
| Disable | Disables command completion, login from a remote console, system memory dumping and rebooting, or a specified interface. |
| Enable | Enables command completion, login from a remote console, system memory dumping and rebooting, or enables a specified interface. |
| Event | Enters the Event Logging System configuration environment. |
| Feature | Provides access to configuration commands for independent device features outside the usual protocol and network interface configuration processes. |
| List | Displays system parameters, hardware configuration, a complete user list. |
| Network | Enters the configuration environment of the specified network. |
| Patch | Modifies the device's global configuration. |
| Performance | Provides a snapshot of the main processor utilization statistics. |
| Protocol | Enters the command environment of the specified protocol. |
| Set | Sets system-wide parameters for buffers, host name, inactivity timer, packet size, prompt level, number of spare interfaces, dump parameters, location, and contact person. |
| Time | Keeps track of system time and displays it on the console. |
| Unpatch | Restores patch variables to default values. |
Use the add command to add user-access.
Syntax:
When the first user is added, console login is automatically enabled. Each user added must be assigned one of the permission levels defined in the table below.
When users are added, set login authentication to local. Otherwise a
remote server must be used.
| Permission Level | Description |
|---|---|
| Administrator (A) | Displays configuration and user information, adds/modifies/deletes configuration and user information. The Administrator can access any device function. |
| Operator (O) | Views device configuration, views statistics, runs potentially disruptive tests, dynamically changes device operation, and restarts the device. Operators cannot modify the permanent device configuration. All actions can be undone with a system restart. |
| Monitor (M) | Views device configuration and statistics but cannot modify or disrupt the operation of the device. |
| Tech Support | Allows your service representative to gain access to the device if a password is forgotten. Cannot be assigned to users. |
| Note: | To add a user, you must have administrative permission. You do not have to reinitialize the switch after adding a user. |
Example:
add user John Enter password: Enter password again: Enter permission (A)dmin, (O)perations, (M)onitor [A]? Do you want to add Technical Support access? (Yes or [No]):
Use the boot command to enter the Boot CONFIG command environment. For Boot CONFIG information, see "Using BOOT Config to Perform Change Management".
Syntax:
Use the change command to change your own password, or change user information.
Syntax:
| Note: | To change a user, you must have administrative permission. |
Example:
change user User name: [] Change password? (Yes or No) Change permission? (Yes or [No])
Use the clear command to delete the device's configuration information from nonvolatile configuration memory.
Attention: Use this command only after calling your service representative.
Syntax:
To clear a process from nonvolatile configuration memory, enter the clear command and the process name. To clear all information from configuration memory, except for device information, use the clear all command. To clear all information, including the device information, use the clear all command and then the clear device command.
The clear user command clears all user information except the device console login information. This is left as enabled (if it was configured as enabled) even though the default value is "disabled".
Notes:
Example: clear els
You are about to clear all Event Logging configuration information Are you sure you want to do this (Yes or No):
| Note: | The previous message appears for any parameter configuration you are clearing. |
Use the delete command to remove a user. To use the delete command, you must have administrative permission.
Syntax:
Use the disable command to disable command completion, login from a remote console, system memory dumping, rebooting, or a specified interface.
Syntax:
Use the disable command-completion command to disable the automatic command completion function. See "Command Completion" for a discussion of the automatic command completion function.
System reboot not disabled: memory dumping must be disabled first
Use the enable command to enable command completion, login from a remote console, system memory dumping, rebooting, or a specified interface.
Syntax:
Use the enable command-completion command to enable the automatic command completion function, which assists with the command syntax. See "Command Completion" for a discussion of the automatic command completion function.
Warning: Console login is disabled until an administrative user is added.
| Attention: | Before enabling console login, save the configuration with console login disabled. If login authentication is set to a remote server using Radius or Tacacs+ and the device is unable to reach the authentication server, then access to the device is denied. By disabling the console login, a lock-out situation is prevented. |
System memory dump function not enabled: rebooting must be enabled first
See the set dump enable-mode and set dump save-mode commands.
Example:
Config> enable dump Current System Dump Status: System dump is currently disabled. Number of existing dump files: 0 Enable system memory dumping? [No]: Yes Current System Dump Status: System dump is currently enabled. Number of existing dump files: 0
| Note: | If you enter this command and a hard drive is not available, you will receive a message indicating that the drive is unavailable. |
Use the event command to enter the Event Logging System (ELS) environment so that you can define the messages that will appear on the console. Refer to "Using the Event Logging System (ELS)" for information about ELS.
Syntax:
Use the feature command to access configuration commands for specific device features outside of the protocol and network interface configuration processes.
Syntax:
All IBM 8371 features have commands that are executed by:
The procedure for accessing these processes is the same for all features. The following information describes the procedure.
Enter a question mark after the feature command to obtain a listing of the features available for your software release.
To access a feature's configuration prompt, enter the
feature command followed by the feature number or short
name. Table 15 lists available feature numbers and names.
Table 15. IBM 8371 Feature Numbers and Names
|
Feature Number |
Feature Short Name |
Accesses the following feature configuration process |
|---|---|---|
| 6 | QoS | Quality of Service |
| 17 | Self Learning IP | |
| 18 | RMON |
Once you access the configuration prompt for a feature, you can begin entering specific configuration commands for the feature. To return to the CONFIG prompt, enter the exit command at the feature's configuration prompt.
Use the list command to display configuration information for all network interfaces, or configuration information for the device.
Syntax:
Example: list configuration
Hostname: [none] Maximum packet size: [autoconfigured] Maximum number of global buffers: [autoconfigured] Number of spare interfaces: 0 Console inactivity timer (minutes): 0 Physical console login: disabled Command Completion: enabled Contact person for this node: [none] Location of this node: [none] Configurable Protocols: Num Name Protocol 11 SNMP Simple Network Management Protocol 23 ASRT Adaptive Source Routing Transparent Enhanced Bridge 24 HST TCP/IP Host Services 29 MPOA Multi-Protocol Over ATM Configurable Features: Num Name Feature 6 QOS Quality of Service 17 Self Self Learning IP 18 RMON Remote Network Monitor 119168 bytes of configuration memory free
Example: list devices
Ifc 0 1-port 10/100 Ethernet Slot: 0 Port: 1 Ifc 1 1-port 10/100 Ethernet Slot: 0 Port: 2 Ifc 2 1-port 10/100 Ethernet Slot: 0 Port: 3 Ifc 3 1-port 10/100 Ethernet Slot: 0 Port: 4 Ifc 4 1-port 10/100 Ethernet Slot: 0 Port: 5 Ifc 5 1-port 10/100 Ethernet Slot: 0 Port: 6 Ifc 6 1-port 10/100 Ethernet Slot: 0 Port: 7 Ifc 7 1-port 10/100 Ethernet Slot: 0 Port: 8 Ifc 8 1-port 10/100 Ethernet Slot: 0 Port: 9 Ifc 9 1-port 10/100 Ethernet Slot: 0 Port: 10 Ifc 10 1-port 10/100 Ethernet Slot: 0 Port: 11 Ifc 11 1-port 10/100 Ethernet Slot: 0 Port: 12 Ifc 12 1-port 10/100 Ethernet Slot: 0 Port: 13 Ifc 13 1-port 10/100 Ethernet Slot: 0 Port: 14 Ifc 14 1-port 10/100 Ethernet Slot: 0 Port: 15 Ifc 15 1-port 10/100 Ethernet Slot: 0 Port: 16 Ifc 16 1-port 10/100 Ethernet Slot: 1 Port: 1 Ifc 17 1-port 10/100 Ethernet Slot: 1 Port: 2 Ifc 18 1-port 10/100 Ethernet Slot: 1 Port: 3 Ifc 19 1-port 10/100 Ethernet Slot: 1 Port: 4 Ifc 20 1-port 10/100 Ethernet Slot: 1 Port: 5 Ifc 21 1-port 10/100 Ethernet Slot: 1 Port: 6 Ifc 22 1-port 10/100 Ethernet Slot: 1 Port: 7 Ifc 23 1-port 10/100 Ethernet Slot: 1 Port: 8 Ifc 24 1-port 10/100 Ethernet Slot: 2 Port: 1 Ifc 25 1-port 10/100 Ethernet Slot: 2 Port: 2 Ifc 26 1-port 10/100 Ethernet Slot: 2 Port: 3 Ifc 27 1-port 10/100 Ethernet Slot: 2 Port: 4 Ifc 28 1-port 10/100 Ethernet Slot: 2 Port: 5 Ifc 29 1-port 10/100 Ethernet Slot: 2 Port: 6 Ifc 30 1-port 10/100 Ethernet Slot: 2 Port: 7 Ifc 31 1-port 10/100 Ethernet Slot: 2 Port: 8 Ifc 32 Link Aggregation Slot: 3 Port: 1 Ifc 33 Link Aggregation Slot: 3 Port: 2 Ifc 34 Link Aggregation Slot: 3 Port: 3 Ifc 35 Link Aggregation Slot: 3 Port: 4 Ifc 36 ATM Slot: 1 Port: 1 Ifc 37 ATM Slot: 1 Port: 2 Ifc 38 ATM Slot: 2 Port: 1 Ifc 39 ATM Slot: 2 Port: 2
Ifc 40 ATM Ethernet LAN Emulation Ifc 41 ATM Ethernet LAN Emulation Ifc 42 ATM Ethernet LAN Emulation Ifc 43 ATM Ethernet LAN Emulation Ifc 44 ATM Ethernet LAN Emulation Ifc 45 ATM Ethernet LAN Emulation Ifc 46 ATM Ethernet LAN Emulation Ifc 47 ATM Ethernet LAN Emulation Ifc 48 ATM Ethernet LAN Emulation Ifc 49 ATM Ethernet LAN Emulation Ifc 50 ATM Ethernet LAN Emulation Ifc 51 ATM Ethernet LAN Emulation Ifc 52 ATM Ethernet LAN Emulation Ifc 53 ATM Ethernet LAN Emulation Ifc 54 ATM Ethernet LAN Emulation Ifc 55 ATM Ethernet LAN Emulation Ifc 56 ATM Ethernet LAN Emulation Ifc 57 ATM Ethernet LAN Emulation Ifc 58 ATM Ethernet LAN Emulation Ifc 59 ATM Ethernet LAN Emulation Ifc 60 ATM Ethernet LAN Emulation Ifc 61 ATM Ethernet LAN Emulation Ifc 62 ATM Ethernet LAN Emulation Ifc 63 ATM Ethernet LAN Emulation Config>
Example:
list patches Patched variable Value mosheap-lowmark 20
Example:
list users USER PERMISSION joe operations mary administrative peter monitor
Use the network command to enter the network interface configuration environment for supported networks. Enter the interface or network number as part of the command. (To obtain the interface number, use the CONFIG list device command.) The appropriate configuration prompt (for example, TKR Config>) will be displayed. See the network interface configuration chapters in this book for complete information on configuring your types of network interfaces.
Syntax:
Notes:
Use the patch command for modifying the device's global configuration. Patch variables are recorded in nonvolatile configuration memory and take effect immediately; you do not have to wait for the next restart of the device. This command should be used only for handling uncommon configurations. Anything that you commonly configure should still be handled by using the specific configuration commands. The following is a list of the current patch variables documented and supported for this release.
Syntax:
When the operator receives notification, the operator can reconfigure the device and then reboot, minimizing the outage to the network. Specifying 0 for this parameter suppresses this warning.
Valid Values: 0 to 100
Default Value: 10
| Note: | You must specify the complete name of the patch variable that you want to change. You cannot use an abbreviated syntax for the patch name. |
Use the performance command at the Config> prompt to enter the configuration environment for performance. See "Configuring and Monitoring Performance" for more information.
Use the protocol command at the Config> prompt to enter the configuration environment for the protocol software installed in the device.
Syntax:
The protocol command followed by the desired protocol number or short name lets you enter a protocol's command environment. After you enter this command, the prompt of the specified protocol appears. From the prompt, you can enter commands specific to that protocol. To return to Config>, enter the exit command.
Notes:
The changes you make through CONFIG are kept in a configuration database in nonvolatile memory and are recalled when you restart the device.
Use the qconfig command to initiate Quick Config. Quick Config allows you to configure parameters for bridging and routing protocols without entering separate configuration environments.
Syntax:
Use the set command to configure various system-wide parameters.
Syntax:
This variable is for information purposes only and has no effect on device operation. It is useful for SNMP management identification of the system.
The set down-notify command is used primarily when tunneling LLC traffic over an IP network using OSPF. If an interface goes down, OSPF cannot detect it fast enough because of the length of time that it takes for an interface to be declared down. Therefore, LLC sessions would begin to timeout. You can set the down-notify timer to a lower value, allowing OSPF to sense that an interface is down quicker. This enables an alternate route to be chosen more quickly, which will prevent the LLC sessions from timing out.
| Note: | If the set down-notify command is executed on one end of a serial
link, the same command must be performed at the other end of the link or the
link may not come up and stay up.
The list devices command will show the down notification time setting for any interface that has the default value overridden. |
If the target is a network, then IP and TFTP parameters of both the local LAN interface and the remote host are required. An additional parameter determines whether the file will be sent by TFTP as compressed or uncompressed data.
When the system dump file is sent by TFTP to the remote host, it will be written as multiple files, which must first be concatenated. For example, if the remote file was specified as /tmp/dump_to_host, and remote files are sent as compressed. The files written on the remote workstation are:
Depending on the total size of the dump, there may be additional files, named as:
In order to decompress and view the dump information, the files must be combined as follows into a single file (note that order is critical):
/tmp> cat dump_to_host0.cmp dump_to_host0.cm1 dump_to_host0.cm2 dump_to_host0.cm3 > dump_to_host0_cat.cmp
As a result, the combined file dump_to_host0_cat.cmp will contain a complete system memory dump image.
If the file was sent by TFTP as uncompressed, the file extensions are .unc, .un1, .un2, and .un3 instead of .cmp, .cm1, .cm2, and .cm3. The uncompressed files must also be concatenated to create a complete system memory dump image. For Example:
/tmp>cat dump_to_host0.unc dump_to_host0.un1 dump_to_host0.un2 dump_to_host0.un3 > dump_to_host0_cat
| Note: | The output file, dump_to_host0_cat. does not require a file extension because the file is not compressed. |
Lowering the low threshold value will make it less likely that packets from this interface will be dropped when sent on congested networks. However, lowering the value may negatively affect performance if underruns occur because the receive buffer queue is empty. Raising the value has the opposite effect. To determine if underruns are occurring, use the GWCON interface command and specify the interface number. To determine if packets from this interface are being dropped because the low threshold has been reached, use the GWCON (Talk 5) error command and look at the Input Flow Drop counter value for the interface.
The range of values is 1 to 255. The default is both product-specific and device-specific. The low threshold should be less than the requested number of receive buffers. Specifying a value of 0 restores the autoconfigured default.
Use the GWCON (Talk 5) buffer and queue commands to show the low threshold setting.
Interface# is the number of the interface you are configuring. Low_#_of_receive_buffers is the low threshold value.
| Attention: | Use this command only under direct instructions from your service representative. Never use it to reduce packet size - only to increase it. |
The user-defined-name can be any combination of characters, numbers, and spaces up to 80 characters. Special characters may be used to request additional functions as described in Table 16.
Example:
set prompt What is the new MOS prompt [y]? AnyHost 99 AnyHost 99 Config>
Table 16. Additional Functions Provided by the Set Prompt Level Command
| Special Characters | Function Provided by the Set Prompt Level Command | ||
|---|---|---|---|
| $n | Displays the hostname. This is useful when you want the hostname
included in the prompt. For example:
| ||
| $t | Displays the time. For example:
| ||
| $d | Displays the current date-month-year. For example:
| ||
| $v | Displays the software VPD information in the following format: program-product-name Feature xxxx Vx.x PTFx RPQx | ||
| $e | Erases one character after this combination within the user-defined prompt. | ||
| $h | Erases one character before this combination within the user-defined prompt. | ||
| $_ | Adds a carriage return to the user-defined prompt. | ||
| $$ | Displays the $. | ||
| |||
Table 17. Default and Maximum Settings for Interfaces
| Interface | Default | Maximum |
|---|---|---|
| ATM | 80 | 1000 |
| 10/100 Mbps Ethernet | 64 | 1000 |
Use the time command to set the system clock and date, set the clock after a reboot, and to display the values on the user console. These values can then be used to time-stamp ELS messages.
Syntax:
Example: time list 05:20:27 Wednesday December 7, 1994 Set by: operator Time Host: 131.210.4.1 Sync Interval: 10 seconds GMT Offset: -300 minutes
Valid values: -720 to 720
Default value: 0
Example: time set year [1996] 1997 month [12]? date [6]? 7 hour [11]? 12 minute [3]? second [2]?
Use the unpatch command to restore the values of the patch variables entered with the patch command to their default values. See the patch command in "Patch" for details.
Syntax:
| Note: | You must specify the complete name of the patch variable to be restored. |